Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4bbb836dc24c15021fbf023ccc92a1b30cb3becfd949ea159141459241c7d93

Tx prefix hash: 3b39be71f2286106a0a498b389daade2107ba4dc2fdf465bae6934f6ebf84b2e
Tx public key: 601aa7469cae9f917001cfcd6d2d62bf869f407999eb246c9f01116135a9f776
Timestamp: 1646789535 Timestamp [UCT]: 2022-03-09 01:32:15 Age [y:d:h:m:s]: 03:085:14:23:48
Block: 454351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 841376 RingCT/type: yes/0
Extra: 01601aa7469cae9f917001cfcd6d2d62bf869f407999eb246c9f01116135a9f77602110000000abf7ee4e7000000000000000000

1 output(s) for total of 19.166675906000 dcy

stealth address amount amount idx
00: f2fdf90f2c7b62a065bcc22021aeab2bf80b4c48bc3f834a0c24d40ad2ae8144 19.166675906000 869982 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": 454361, "vin": [ { "gen": { "height": 454351 } } ], "vout": [ { "amount": 19166675906, "target": { "key": "f2fdf90f2c7b62a065bcc22021aeab2bf80b4c48bc3f834a0c24d40ad2ae8144" } } ], "extra": [ 1, 96, 26, 167, 70, 156, 174, 159, 145, 112, 1, 207, 205, 109, 45, 98, 191, 134, 159, 64, 121, 153, 235, 36, 108, 159, 1, 17, 97, 53, 169, 247, 118, 2, 17, 0, 0, 0, 10, 191, 126, 228, 231, 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