Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: f47c1c8881c77cc3193d1b516091f1c4d99248b1945f730e73dcc5512ed59bec

Tx prefix hash: b5a94b79bf87640d6dbeafea985735d3e0714a4f133b51062205c22906825eec
Tx public key: 271f30bef8bcd9f1d88ef63ed7dd17e899dab0d94e3536dc94e98a67c704c70b
Timestamp: 1694732207 Timestamp [UCT]: 2023-09-14 22:56:47 Age [y:d:h:m:s]: 01:208:06:57:05
Block: 848262 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 409955 RingCT/type: yes/0
Extra: 01271f30bef8bcd9f1d88ef63ed7dd17e899dab0d94e3536dc94e98a67c704c70b02110000000133af99f4000000000000000000

1 output(s) for total of 0.949196051000 dcy

stealth address amount amount idx
00: 527731caade1b7f3cacf99aea1efb34a61648b4cdfe757ee0e7e1392fafa340e 0.949196051000 1301852 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 848272, "vin": [ { "gen": { "height": 848262 } } ], "vout": [ { "amount": 949196051, "target": { "key": "527731caade1b7f3cacf99aea1efb34a61648b4cdfe757ee0e7e1392fafa340e" } } ], "extra": [ 1, 39, 31, 48, 190, 248, 188, 217, 241, 216, 142, 246, 62, 215, 221, 23, 232, 153, 218, 176, 217, 78, 53, 54, 220, 148, 233, 138, 103, 199, 4, 199, 11, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8