Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 504c4110742d59d08823301434e1676362be339cc3091b1843655971f7047530

Tx prefix hash: 4abd0c1dda8c14b0f886e9f0742c0bcf7e5bd3ec4fb3c2051dc1a4db64a360da
Tx public key: e1a56b61cce2cd8124d2ba488df97c4281c33af86b7cb3c23b0a404167d0a1d6
Timestamp: 1677511322 Timestamp [UCT]: 2023-02-27 15:22:02 Age [y:d:h:m:s]: 01:363:23:38:26
Block: 706185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 520826 RingCT/type: yes/0
Extra: 01e1a56b61cce2cd8124d2ba488df97c4281c33af86b7cb3c23b0a404167d0a1d60211000000017e406890000000000000000000

1 output(s) for total of 2.806182086000 dcy

stealth address amount amount idx
00: 6c6f8ce4b703a1ea9834098315c7dd956d72e82310bed9df73c4dc2eb6ed0fb4 2.806182086000 1149910 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": 706195, "vin": [ { "gen": { "height": 706185 } } ], "vout": [ { "amount": 2806182086, "target": { "key": "6c6f8ce4b703a1ea9834098315c7dd956d72e82310bed9df73c4dc2eb6ed0fb4" } } ], "extra": [ 1, 225, 165, 107, 97, 204, 226, 205, 129, 36, 210, 186, 72, 141, 249, 124, 66, 129, 195, 58, 248, 107, 124, 179, 194, 59, 10, 64, 65, 103, 208, 161, 214, 2, 17, 0, 0, 0, 1, 126, 64, 104, 144, 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