Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da01076c4f6e7738acaa392c2bda203bd636f572ecd71b8f6f04c3ce07e35801

Tx prefix hash: b93400fe15208f1003cf0a4a580b9ecdc48071e3cab77932d18750bcd1127e39
Tx public key: 88557b99f14fc44f80e81d4b62d553143582d0e2c9cd03ea7a3cfb15a6bf9c51
Timestamp: 1702733113 Timestamp [UCT]: 2023-12-16 13:25:13 Age [y:d:h:m:s]: 01:330:08:01:39
Block: 914398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 494952 RingCT/type: yes/0
Extra: 0188557b99f14fc44f80e81d4b62d553143582d0e2c9cd03ea7a3cfb15a6bf9c5102110000001bfaf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84225340e2d0a217ab26ed7d4e92ac3364193b5edc36c89e1673e278b52ea3f2 0.600000000000 1371712 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": 914408, "vin": [ { "gen": { "height": 914398 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84225340e2d0a217ab26ed7d4e92ac3364193b5edc36c89e1673e278b52ea3f2" } } ], "extra": [ 1, 136, 85, 123, 153, 241, 79, 196, 79, 128, 232, 29, 75, 98, 213, 83, 20, 53, 130, 208, 226, 201, 205, 3, 234, 122, 60, 251, 21, 166, 191, 156, 81, 2, 17, 0, 0, 0, 27, 250, 243, 92, 156, 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