Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3328f3479096f61c8fea64016ce4e2ef4b5f95b2bf0a8725ed651518ad3375e8

Tx prefix hash: bcc8684636d318707b84b593d91f090ea1ba2f1eb9c3bbd71cefd2ad330d5c49
Tx public key: 6049ace803954a1403fc3af4091f9c88b042b64fe6c728f138dd218a89c6fd95
Timestamp: 1734748590 Timestamp [UCT]: 2024-12-21 02:36:30 Age [y:d:h:m:s]: 00:101:07:11:46
Block: 1179738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72150 RingCT/type: yes/0
Extra: 016049ace803954a1403fc3af4091f9c88b042b64fe6c728f138dd218a89c6fd95021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2e5984b5f7e855be75c0de56fafde754ec9ed83e0156c67c0fed217a1acdc8e 0.600000000000 1666137 of 15

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": 1179748, "vin": [ { "gen": { "height": 1179738 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2e5984b5f7e855be75c0de56fafde754ec9ed83e0156c67c0fed217a1acdc8e" } } ], "extra": [ 1, 96, 73, 172, 232, 3, 149, 74, 20, 3, 252, 58, 244, 9, 31, 156, 136, 176, 66, 182, 79, 230, 199, 40, 241, 56, 221, 33, 138, 137, 198, 253, 149, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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