Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4b149a5edc3286e9a335e540349eeb344413b2c7c3aaaa29358133844257650

Tx prefix hash: 1293214f7c8409a5c4046f337c22e1cc908301720fac1f0d816f77867749f9fc
Tx public key: 70d8d4cb7afbbfbe7cef77baae90c21bafe8e9b1626d138e9121f4d2124aea39
Timestamp: 1628958976 Timestamp [UCT]: 2021-08-14 16:36:16 Age [y:d:h:m:s]: 03:138:00:48:54
Block: 314005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 871865 RingCT/type: yes/0
Extra: 0170d8d4cb7afbbfbe7cef77baae90c21bafe8e9b1626d138e9121f4d2124aea3902110000004a01f1e57f000000000000000000

1 output(s) for total of 55.920565591000 dcy

stealth address amount amount idx
00: eb27b3d751845980b770ce27465cea14e6d39250d0af1b991843a879634c5144 55.920565591000 653598 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": 314015, "vin": [ { "gen": { "height": 314005 } } ], "vout": [ { "amount": 55920565591, "target": { "key": "eb27b3d751845980b770ce27465cea14e6d39250d0af1b991843a879634c5144" } } ], "extra": [ 1, 112, 216, 212, 203, 122, 251, 191, 190, 124, 239, 119, 186, 174, 144, 194, 27, 175, 232, 233, 177, 98, 109, 19, 142, 145, 33, 244, 210, 18, 74, 234, 57, 2, 17, 0, 0, 0, 74, 1, 241, 229, 127, 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